Summary

This PR adds the ability for users to rename workflow nodes directly from the UI.

Why This is Useful

When building complex workflows, users often have multiple instances of the same component type. For example:

• Multiple HTTP Request nodes fetching from different APIs
• Multiple Script nodes performing different transformations
• Multiple Slack nodes alerting different channels

Without custom naming, users see generic labels like "HTTP Request", "Script", "Slack" everywhere, making it hard to understand the workflow at a glance.

With this feature, users can give context-specific names:

• "Fetch Threat Feed" instead of "HTTP Request"
• "Extract Suspicious IP" instead of "Script / Logic"
• "Alert Security Team" instead of "Slack"

The original component type is still visible as a subscript, so users always know what type of node it is while having the descriptive name front and center.

Features

In ConfigPanel (Component Info Section):

• Displays the custom node name (or component name as fallback)
• Pencil icon appears on hover to edit the name
• Inline input with check button when editing
• Shows component name as subscript when a custom name is set

On the Node itself (WorkflowNode):

• Double-click on node label to edit inline
• Shows component name as subscript when a custom name is set
• Press Enter to save, Escape to cancel, or click outside to save

Design Decisions

• Entry Point nodes cannot be renamed (they're special)
• Only available in Design mode
• Compact UI - merged into component info section, no extra space taken
• Marks workflow dirty when label is changed